Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

0955

reference
326-tree-1
name
0955
tree-preservation-order

undefined

326-tpo-1
uprn
address-text
point
POINT (-1.018251 50.866821)
geometry
MULTIPOLYGON (((-1.018180 50.866814,-1.018184 50.866828,-1.018193 50.866840,-1.018209 50.866850,-1.018229 50.866857,-1.018250 50.866859,-1.018272 50.866857,-1.018292 50.866851,-1.018308 50.866841,-1.018319 50.866829,-1.018322 50.866815,-1.018319 50.866801,-1.018309 50.866788,-1.018294 50.866778,-1.018274 50.866772,-1.018252 50.866769,-1.018230 50.866771,-1.018210 50.866778,-1.018194 50.866787,-1.018184 50.866800,-1.018180 50.866814)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL